Skip to main content
TrustRadius
Puppet Enterprise

Puppet Enterprise

Overview

What is Puppet Enterprise?

Puppet Enteprise is an IT automation and configuration management solution that enables users to manage and automate infrastructure and complex workflows. The vendor states Puppet Enterprise combines both model‑based and task-based capabilities in a way that enables organizations to scale…

Read more
Recent Reviews

TrustRadius Insights

Puppet is a versatile tool that is widely used across organizations to streamline operations and automate various tasks. Users rely on …
Continue reading

Puppet is a great tool

9 out of 10
February 12, 2016
Incentivized
We use Puppet Data Center Automation as a configuration management tool in our organization. It allows us to maintain a constant baseline …
Continue reading
Read all reviews
Return to navigation

Pricing

View all pricing
N/A
Unavailable

What is Puppet Enterprise?

Puppet Enteprise is an IT automation and configuration management solution that enables users to manage and automate infrastructure and complex workflows. The vendor states Puppet Enterprise combines both model‑based and task-based capabilities in a way that enables organizations to scale their…

Entry-level set up fee?

  • No setup fee

Offerings

  • Free Trial
  • Free/Freemium Version
  • Premium Consulting/Integration Services

Would you like us to let the vendor know that you want pricing?

11 people also want pricing

Alternatives Pricing

What is AWS CloudFormation?

AWS CloudFormation gives developers and systems administrators a way to create and manage a collection of related AWS resources, provisioning and updating them in a predictable fashion. Use AWS CloudFormation’s sample templates or create templates to describe the AWS resources, and any associated…

Return to navigation

Product Demos

Puppet Enterprise Demo - Silicon Valley Puppet Camp 2014

YouTube

Demo of Puppet Enterprise Supported Modules

YouTube

Keep your IT infrastructure in a known good state with Puppet Enterprise

YouTube

Puppe Enterprise Openstack Icehouse Demo

YouTube

Puppet Enterprise 2019 Console Walkthrough Demo

YouTube

Automate IT: Getting Started with Puppet Enterprise

YouTube
Return to navigation

Product Details

Puppet Enterprise Technical Details

Operating SystemsUnspecified
Mobile ApplicationNo
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

(53)

Community Insights

TrustRadius Insights are summaries of user sentiment data from TrustRadius reviews and, when necessary, 3rd-party data sources. Have feedback on this content? Let us know!

Puppet is a versatile tool that is widely used across organizations to streamline operations and automate various tasks. Users rely on Puppet to maintain configuration and deploy new versions of applications throughout their infrastructure. With variables stored in Hiera, Puppet allows for easy roll-out of configuration changes across all parts of the system. It also serves as a reliable deployment tool, enabling quick and consistent deployment and maintenance of various systems.

One of the key use cases of Puppet is automating redundant tasks and simplifying the deployment of complex system configurations. By automating installations and configuring environments after the initial OS install, Puppet greatly reduces manual effort and ensures consistent configurations. Additionally, Puppet is utilized to automate deployments and ensure configuration consistency across multiple data centers, making it scalable and efficient.

Another important use case is managing server lifecycle and automating provisioning, configuration changes, and removal of dynamic resources. Puppet Data Center Automation is particularly useful in standardizing server deployments, maintaining a uniform configuration, and ensuring timely updates and account provisioning or deprovisioning.

Moreover, Puppet plays a vital role in establishing communication between the master server and other computers, guaranteeing access to up-to-date files. It is also commonly integrated with other open-source tools to automate virtual machines. Furthermore, users have found value in Puppet for solving business problems and supporting open-source software.

Overall, Puppet has proven to be a valuable asset for organizations looking to automate and streamline their operations. Its wide range of use cases, from maintaining configuration to deploying and managing systems, make it a powerful tool for various industries.

Reliable mechanism for deploying infrastructure-as-code: Users have found Puppet to be a dependable solution for deploying infrastructure-as-code, particularly when integrated with source control platforms like Git. Several reviewers have mentioned that it ensures system stability and uptime by effectively managing configuration drift.

Valuable asset for transitioning to DevOps: Puppet is highly regarded as a valuable tool for teams embracing DevOps practices. It empowers development teams to take ownership of their assets and automates repetitive tasks. This streamlines system management and simplifies complex operations.

Seamless integration with other community projects: Many users appreciate Puppet's seamless integration capabilities with various community/open-source projects such as Cobbler and Foreman. This integration enhances its ability to automate software installations and configure software post-installation effectively.

Confusing Execution of Actions: Some users have found the execution of actions in Puppet to be confusing, particularly when it comes to declaring the order of execution for tasks. This has caused difficulties in understanding and managing the workflow within Puppet.

Difficulty with Parallel Execution: Several users have expressed challenges in executing commands across multiple hosts in parallel, which they found convenient in Chef's knife command. The absence of this feature in Puppet has hindered their ability to efficiently manage and control large-scale deployments.

Limitations on Language and Integration: Users have mentioned limitations with Puppet's language and integration capabilities. They have experienced issues with the lack of support for inline Ruby, making it difficult to pull data from a database and incorporate it into a manifest effectively. Additionally, some users feel that implementing Puppet requires a significant shift in thinking and procedures as it may not fit well with existing infrastructure.

Based on user reviews, there are three common recommendations for Puppet. First, users advise utilizing Puppet Enterprise and consulting professional services for installation to ensure a smoother setup process and access to expert guidance. Second, it is highly recommended to get trained in Puppet and attend the Puppetize Live conference to gain a deeper understanding of the tool and stay updated with the latest developments. Lastly, users suggest exploring the Puppet Forge for pre-built modules and resources, as this library of modules can significantly enhance automation capabilities and simplify complex tasks. By following these recommendations, users can maximize their experience with Puppet and leverage its benefits effectively.

Attribute Ratings

Reviews

(1-1 of 1)
Companies can't remove reviews or game the system. Here's why
Score 7 out of 10
Vetted Review
Verified User
Incentivized
We host and manage 'a lot' of servers. Many years back without automation we used to run scripts to spin up servers and before that, we used to spend hours doing everything manually on bare metal servers. Once automation came in we initially started playing with Ansible to test the waters but what really grabbed our attention was the pull ability of the Puppet compared to the push ability of Ansible that really got us into a Puppet. For example, when we were still new we had to push configs to each server, and if there is a change on the box we have to push it manually again to all the boxes. So this was not really scalable for us. That's where we started using Puppets. With puppets agents, all we had to do was maintain a code repo and Puppet will pull the configs from the repo. That was the one feature that we were looking for at that time.
  • Puppet manages all our server's "state" so if there is an unauthorized change on the server then in a set interval puppet will run and reset the "state" of the server back to a good working condition. this helps us avoid unauthorized change and also maintains a healthy server.
  • Puppet helps us keep a centralized repo of all the configs that we need to push to the endpoints. Spinning up new servers in AWS/VMWARE/AZURE is a breeze with Puppet.
  • Puppet servers check into our central repo for changes on the code and if it finds any change it will immediately apply the change to the servers. So as admins we don't need to log in to any of the servers manually to make any changes.
  • The setup of Puppet is a nightmare compared to Ansible. Anyone watching a youtube video can easily set up Ansible with minimal IT knowledge. All one needs is the source IP addresses and we are good to go. Setting up Puppet is a more hands-on task and pushing the puppet agents to all the boxes is another issue. If the installation and setup were simplified like Ansible that would attract a lot of people to this platform
  • The syntax of the code for Puppet is not as easy as Ansible. Ansible simply follows a YAML format and it's like typing in normal English. Even complicated tasks can be written by just understanding YAML syntax. Perhaps Puppet needs to revisit the lanugage used and try to come up with a much simpler lanugage for writing code. This will make day-to-day usage easier.
Puppet is the go-to tool if you are working in a static environment where changes are minimal. For instance, if you want to spin up 100 serves and then you just need to maintain it then puppet is the best tool for you. The reason I say that is because Puppet has a complicated syntax language (Ruby) you need to learn. So once a puppet code is written you can simply install the agents and make the agents talk to the master to check for changes. So maintaining an environment is easier. But if your environment is dynamic i.e it keeps changing every other day and you need to write a new config to spin up new devices, then Ansible is the tool for you because writing a playbook on Ansible is very easy.
  • The most important feature that puppet offers is its client agents. These tiny programs are the workers that help us maintain our infrastructure. They keep polling the centralized server and maintaining our servers.
  • Puppet helps us audit all changes that are being done to the server. The reason is once the Puppet agent is installed if there is a change in state, Puppet will automatically revert the change back to the previous state. So the only way to make changes is through the Puppet centralized repo which can even be hosted in Github and sent via Jenkins.
  • Puppet makes spinning up servers and services very easy. For examply you can write a code to spin up a server once and then you can use the same code a hundred times to spin up the same server. You dont need to do anything via console or through the UI.
  • With all the DevOps and automation that we have going on, we save a ton of time on the configuration of the server. It's safe to say that configuring servers via console or via UI is a thing of the past.
  • We try to get all the things done by using a centralized repo (GitHub). Puppet is one tool that actually gets the actual work done.
  • The small amount that we spent on purchasing premium Puppet is completely justified because of the time and effort that this tool actually helps us save.
As I mentioned before Ansible is a great tool. There is no question about it. It has very simple syntax (YAML), is very easy to learn, and is scalable as well. But the only thing that Ansible lacked at that time was the actual agent that have to go into each server. Ansible follows the push method for sending configs to the end server. So all changes have to be pushed to all of your fleets manually. Puppet's agent will pull the config straight from the code repo so you just need to write something in your repo and puppet will pull it and do the tasks. That was the model that we actually needed. Both these products are competitive when it comes to pricing. But if our use case was different we would have gone with Ansible instead of Puppet.
Puppet has top class support. You can simply mail them with their query and they will respond to your query in a timely manner. We do have enterprise license for puppet. Also there is a vibrant community for puppet out there. So even if you dont purchase a premium support option you can simply google your queries and get answers.
We do have premium support for puppet. We maintain support agreement for almost all the products that we purchase. We dont want to get into a situation where we run into problems with a mission critical app and there is no support. Also the price for puppet support is not that much. Its fairly reasonalble.
No
Return to navigation